u-boot-xlnx: Avoid breaking compatibility with posix sh#66
Open
ngenetzky-at-appareo wants to merge 1 commit into
Open
Conversation
Contributor
|
Thanks for the patch, since langdale-next is closed we can consider this for scarthgap release. |
Author
|
@grsandeep85 , it has already been fixed in the scarthgap branch. Xilinx 2024.1 choose to use Langdale instead of the Kirkstone LTS. Some of us need to keep building for older versions. I hope you reconsider your branching if you expect others to utilize your BSP. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NOTE: First time contributor to this repo. Please let me know of any guidelines for contributing that I might not be aware of.
BitBake recipes and class files are primarily written to be shell-agnostic, aiming for compatibility with /bin/sh, which may be dash or other minimal shells instead of bash. Thus, it is advisable to avoid bash-specific syntax (bashisms) to ensure portability and prevent unexpected behavior.
To avoid bashisms in BitBake:
By adhering to these guidelines, one can create more robust and portable BitBake recipes and class files, avoiding issues related to bash dependencies.